Method of transmitting data, user equipment, network side device and computer readable storage medium

ABSTRACT

A method of transmitting data, a UE, a network side device and a computer readable storage medium are provided. The method of transmitting data is applicable to the UE and includes: transmitting, by the UE, duplicated transmission data to different radio link control (RLC) entities respectively when a network side configures or activates a packet duplication mode for a bearer; transmitting, by one of the different RLC entities, the transmission data through one of logical channels to a master medium access control (MAC) entity and transmitting, by each of the others of the different RLC entities, the transmission data through a different one of the logical channels to a different one of one or more secondary MAC entities; and transmitting, by the master MAC entity and the one or more secondary MAC entities, the transmission data to the network side through different carriers.

CROSS-REFERENCE TO RELATED APPLICATION

The present application claims a priority of the Chinese patentapplication No. 201710183006.0 filed in China on Mar. 24, 2017, adisclosure of which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

This disclosure relates to the field of communication technology, inparticular to a method of transmitting data, a User Equipment (UE), anetwork side device and a computer readable storage medium.

BACKGROUND

5G New Radio (NR) systems mainly support three types of services: 1)enhanced Mobile Broadband (eMBB); 2) massive Machine Type Communications(mMTC); and 3) Ultra-Reliable and Low Latency Communications). ForURLLC, a solution proposed by 3GPP to address URLLC's high demand interms of latency and reliability is packet duplication, i.e.,transmitting the same transmission data through a plurality of logicalchannels, so as to improve transmission reliability and reducetransmission latency.

Referring to FIG. 1, a schematic diagram showing the packet duplicationmodel in related art is illustrated, in which a packet duplication basedon Packet Data Convergence Protocol (PDCP) layer is taken as an example.It can be seen from FIG. 1 that one Radio Bearer (RB) of PDCP layer(each RB corresponds to one PDCP entity) is transmitted through aplurality of logical channels in Radio Link Control (RLC) layerrespectively (each logical channel corresponds to one RLC entity).However, there is no conclusive answer to the problem as to how totransmit a bearer for which packet duplication is enabled in MediumAccess Control (MAC) layer.

SUMMARY

In view of above mentioned, this disclosure provides a method oftransmitting data, a UE and a network side device so as to address theproblem as to how to transmit a bearer for which packet duplication isenabled in the MAC layer.

To solve the aforementioned technical problem, this disclosure providesa method of transmitting data applied to a UE including: transmitting,by the UE, duplicated transmission data to different radio link control(RLC) entities respectively when a network side configures or activatesa packet duplication mode for a bearer; transmitting, by one of thedifferent RLC entities, the transmission data through one of logicalchannels to a master medium access control (MAC) entity andtransmitting, by each of the others of the different RLC entities, thetransmission data through a different one of the logical channels to adifferent one of one or more secondary MAC entities; and transmitting,by the master MAC entity and the one or more secondary MAC entities, thetransmission data to the network side through different carriers.

Optionally, each of the logical channels corresponds to one RLC entityand each of the logical channels corresponds to one MAC entity.

Optionally, the one or more secondary MAC entities are establishedtogether with the master MAC entity.

Optionally, the method further includes: establishing, the UE, the oneor more secondary MAC entities corresponding to the bearer for whichpacket duplication mode is configured or activated when the network sideconfigures or activates the packet duplication mode for the bearer.

Optionally, the method further includes: releasing, by the UE, the oneor more secondary MAC entities corresponding to the bearer for whichpacket duplication mode is configured or activated when the network sidedeconfigures or deactivates the packet duplication mode for the bearer.

Optionally, prior to the transmitting, by the UE, the duplicatedtransmission data to the different RLC entities respectively, the methodfurther includes: receiving a mapping between the carriers and themaster MAC entity and the one or more secondary MAC entities that isconfigured by the network side semi-statically or dynamically.

Optionally, prior to the transmitting, by the UE, the duplicatedtransmission data to the different RLC entities respectively, the methodfurther includes: receiving a mapping between the logical channels andthe master MAC entity and the one or more secondary MAC entities or amapping between the logical channels and the carriers that is configuredby the network side semi-statically or dynamically.

Optionally, both the master MAC entity and the one or more secondary MACentities are configured to bear a logical channel corresponding to abearer for which packet duplication mode is not configured or activatedand logical channels corresponding to a bearer for which packetduplication mode is configured or activated.

Optionally, when one of the one or more secondary MAC entities isreleased, the logical channel corresponding to the bearer for whichpacket duplication mode is not configured or activated that is borne onthe released one of the one or more secondary MAC entities isautomatically transferred to be borne on the master MAC entity.

Optionally, the master MAC entity is configured to bear a logicalchannel corresponding to a bearer for which packet duplication mode isnot configured or activated and logical channels corresponding to abearer for which packet duplication mode is configured or activated; andthe one or more secondary MAC entities are configured to only bearlogical channels corresponding to a bearer for which packet duplicationmode is configured or activated.

Optionally, the method further includes: determining whether to triggera buffer state reporting (BSR); and reporting to the network side buffersizes of the logical channels or logical channel groups corresponding tothe master MAC entity and the one or more secondary MAC entities when itis determined the BSR is to be triggered.

Optionally, the determining whether to trigger the BSR is performedbased on the UE.

Optionally, the reporting to the network side the buffer sizes of thelogical channels or logical channel groups corresponding to the masterMAC entity and the one or more secondary MAC entities includes:reporting to the network side the buffer sizes of the logical channelsor logical channel groups corresponding to the master MAC entity and theone or more secondary MAC entities by using a carrier corresponding toany one MAC entity of the master MAC entity and the one or moresecondary MAC entities.

Optionally, the reporting to the network side the buffer sizes of thelogical channels or logical channel groups corresponding to the masterMAC entity and the one or more secondary MAC entities includes:reporting to the network side the buffer sizes of the logical channelsor logical channel groups corresponding to the master MAC entity and theone or more secondary MAC entities through one BSR MAC CE.

Optionally, the reporting to the network side the buffer sizes of thelogical channels or logical channel groups corresponding to the masterMAC entity and the one or more secondary MAC entities includes:reporting to the network side the buffer sizes of the logical channelsor logical channel groups corresponding to the master MAC entity and theone or more secondary MAC entities through a plurality of BSR MAC CEs inone MAC PDU.

Optionally, the determining whether to trigger the BSR is performedbased on a MAC entity.

Optionally, the reporting to the network side the buffer sizes of thelogical channels or logical channel groups corresponding to the masterMAC entity and the one or more secondary MAC entities includes:reporting to the network side the buffer sizes of the logical channelsor logical channel groups corresponding to the master MAC entity and theone or more secondary MAC entities by using a carrier corresponding tothe MAC entity or a carrier corresponding to other MAC entity.

Optionally, the reporting to the network side the buffer sizes of thelogical channels or logical channel groups corresponding to the masterMAC entity and the one or more secondary MAC entities includes: addingidentification information in the BSR MAC CE to identify acorrespondence between the logical channels or logical channel groupsand the MAC entities when a carrier used in BSR MAC CE transmission isnot limited and there is a repetition of ID among the logical channelsor logical channel groups corresponding to different MAC entities.

Optionally, prior to the transmitting, by the UE, the duplicatedtransmission data to the different RLC entities respectively, the methodfurther comprises: transmitting a UE capability to the network side, theUE capability carrying capability indication information indicating thatthe bearer using packet duplication mode is supported.

This disclosure further provides a method of transmitting data appliedto a network side device including: receiving, by a master medium accesscontrol (MAC) entity and one or more secondary MAC entities of a networkside device, duplicated transmission data transmitted by a userequipment (UE) through different carriers when a packet duplication modeis configured or activated for a bearer; transmitting, by the master MACentity and the one or more secondary MAC entities, the transmission datato different radio link control (RLC) entities through different logicalchannels; and transmitting, by the RLC entities, received transmissiondata to a Packet Data Convergence Protocol (PDCP) entity.

Optionally, each of the logical channels corresponds to one RLC entityand each of the logical channels corresponds to one MAC entity.

Optionally, bearer duplication is performed by the PDCP entity or aprotocol layer on top of PDCP layer.

Optionally, the one or more secondary MAC entities are establishedtogether with the master MAC entity.

Optionally, the method further includes: establishing the one or moresecondary MAC entities corresponding to the bearer for which packetduplication mode is configured or activated when the packet duplicationmode for the bearer is configured or activated; or establishing the oneor more secondary MAC entities corresponding to the bearer for which thepacket duplication mode is configured or activated when the network sidedevice configures or activates packet duplication mode for a first UE ofall UEs served by the network side device.

Optionally, the method further includes: releasing the one or moresecondary MAC entities corresponding to the bearer for which packetduplication mode is configured or activated when the packet duplicationmode for the bearer is deconfigured or deactivated; or releasing the oneor more secondary MAC entities corresponding to the bearer for whichpacket duplication mode is configured or activated when the packetduplication mode for a last bearer for which packet duplication mode isconfigured or activated of all bearers served by the network side deviceis deconfigured or deactivated.

Optionally, the method further includes: setting semi-statically ordynamically a mapping between the carriers and the master MAC entity andthe one or more secondary MAC entities, and transmitting the mapping tothe UE when the packet duplication mode for the bearer is configured oractivated.

Optionally, the method further includes: setting semi-statically ordynamically a mapping between the logical channels and the master MACentity and the one or more secondary MAC entities or a mapping betweenthe logical channels and the carriers, and transmitting the mapping tothe UE when the packet duplication mode for the bearer is configured oractivated.

Optionally, both the master MAC entity and the one or more secondary MACentities are configured to bear a logical channel corresponding to abearer for which packet duplication mode is not configured or activatedand logical channels corresponding to a bearer for which packetduplication mode is configured or activated.

Optionally, when one of the one or more secondary MAC entities isreleased, the logical channel corresponding to the bearer for whichpacket duplication mode is not configured or activated that is borne onthe released one of the one or more secondary MAC entities isautomatically transferred to be borne on the master MAC entity.

Optionally, the master MAC entity is configured to bear a logicalchannel corresponding to a bearer for which packet duplication mode isnot configured or activated and logical channels corresponding to abearer for which packet duplication mode is configured or activated; andthe one or more secondary MAC entities are configured to only bearlogical channels corresponding to a bearer for which packet duplicationmode is configured or activated.

Optionally, the method further includes: receiving buffer sizes,reported by the UE, of the logical channels or logical channel groupscorresponding to the master MAC entity and the one or more secondary MACentities of the UE, and performing uplink resource scheduling based onthe buffer sizes of the logical channels or logical channel groupscorresponding to the master MAC entity and the one or more secondary MACentities of the UE.

Optionally, before the packet duplication mode is configured oractivated for a bearer, the method further comprises: receiving a UEcapability transmitted by the UE, the UE capability carrying capabilityindication information indicating that the bearer using packetduplication mode is supported.

This disclosure further provides a UE, including: a first transmissionmodule, configured to transmit duplicated transmission data to differentradio link control (RLC) entities respectively when a network sideconfigures or activates a packet duplication mode for a bearer; a secondtransmission module, configured to trigger one of the different RLCentities to transmit the transmission data through one of logicalchannels to a master medium access control (MAC) entity andtransmitting, by each of the others of the different RLC entities, thetransmission data through a different one of the logical channels to adifferent one of one or more secondary MAC entities; and a thirdtransmission module, configured to trigger the master MAC entity and theone or more secondary MAC entities to transmit the transmission data tothe network side through different carriers.

Optionally, each of the logical channels corresponds to one RLC entityand each of the logical channels corresponds to one MAC entity.

Optionally, the UE further includes: a first establishment module,configured to establish the one or more secondary MAC entities togetherwith the master MAC entity.

Optionally, the UE further includes: a second establishment module,configured to establish the one or more secondary MAC entitiescorresponding to the bearer for which packet duplication mode isconfigured or activated when the network side configures or activatesthe packet duplication mode for the bearer.

Optionally, the UE further includes: a releasing module, configured torelease the one or more secondary MAC entities corresponding to thebearer for which packet duplication mode is configured or activated whenthe network side deconfigures or deactivates the packet duplication modefor the bearer.

Optionally, the UE further includes: a first reception module,configured to receive a mapping between the carriers and the master MACentity and the one or more secondary MAC entities that is configured bythe network side semi-statically or dynamically.

Optionally, the UE further includes: a second reception module,configured to receive a mapping between the logical channels and themaster MAC entity and the one or more secondary MAC entities or amapping between the logical channels and the carriers that is configuredby the network side semi-statically or dynamically.

Optionally, both the master MAC entity and the one or more secondary MACentities are configured to bear a logical channel corresponding to abearer for which packet duplication mode is not configured or activatedand logical channels corresponding to a bearer for which packetduplication mode is configured or activated.

Optionally, the UE further includes: a transferring module, configuredto automatically transfer the logical channel corresponding to thebearer for which packet duplication mode is not configured or activatedthat is borne on the released one of the one or more secondary MACentities to be borne on the master MAC entity when one of the one ormore secondary MAC entities is released.

Optionally, the master MAC entity is configured to bear a logicalchannel corresponding to a bearer for which packet duplication mode isnot configured or activated and logical channels corresponding to abearer for which packet duplication mode is configured or activated; andthe one or more secondary MAC entities are configured to only bearlogical channels corresponding to a bearer for which packet duplicationmode is configured or activated.

Optionally, the UE further includes: a determination module, configuredto determine whether to trigger a BSR; and a reporting module,configured to report to the network side buffer sizes of the logicalchannels or logical channel groups corresponding to the master MACentity and the one or more secondary MAC entities when it is determinedthe BSR is to be triggered.

Optionally, the determination module determines whether to trigger theBSR based on the UE.

Optionally, the reporting module is further configured to report to thenetwork side the buffer sizes of the logical channels or logical channelgroups corresponding to the master MAC entity and the one or moresecondary MAC entities by using a carrier corresponding to any one MACentity of the master MAC entity and the one or more secondary MACentities.

Optionally, the reporting module is further configured to report to thenetwork side the buffer sizes of the logical channels or logical channelgroups corresponding to the master MAC entity and the one or moresecondary MAC entities through one BSR MAC CE.

Optionally, the reporting module is further configured to report to thenetwork side the buffer sizes of the logical channels or logical channelgroups corresponding to the master MAC entity and the one or moresecondary MAC entities through a plurality of independent BSR MAC CEs inone MAC PDU.

Optionally, the determination module determines whether to trigger theBSR based on a MAC entity.

Optionally, the reporting module is further configured to report to thenetwork side the buffer sizes of the logical channels or logical channelgroups corresponding to the master MAC entity and the one or moresecondary MAC entities by using a carrier corresponding to the MACentity or a carrier corresponding to other MAC entity.

Optionally, the reporting module is further configured to addidentification information in the BSR MAC CE to identify acorrespondence between the logical channels or logical channel groupsand the MAC entities when a carrier used in BSR MAC CE transmission isnot limited and there is a repetition of ID among the logical channelsor logical channel groups corresponding to different MAC entities.

Optionally, the UE further includes: a UE capability transmissionmodule, configured to transmit a UE capability to the network side,wherein the UE capability carries capability indication informationindicating that the bearer using packet duplication mode is supported.

This disclosure further provides a network side device, including: areception module, configured to trigger a master MAC entity and one ormore secondary MAC entities to respectively receive duplicatedtransmission data transmitted by a user equipment (UE) through differentcarriers when a packet duplication mode is configured or activated for abearer; a first transmission module, configured to trigger the masterMAC entity and the one or more secondary MAC entities to transmit thetransmission data to different radio link control (RLC) entities throughdifferent logical channels, a second transmission module, configured totrigger the RLC entities to transmit received transmission data to aPacket Data Convergence Protocol (PDCP)entity.

Optionally, each of the logical channels corresponds to one RLC entityand each of the logical channels corresponds to one MAC entity.

Optionally, the network side device further includes: a bearerduplication module, configured to trigger the PDCP entity or a protocollayer on top of PDCP layer to perform bearer duplication.

Optionally, the network side device further includes: a firstestablishment module, configured to establish the one or more secondaryMAC entities together with the master MAC entity.

Optionally, the network side device further includes: a secondestablishment module, configured to establish the one or more secondaryMAC entities corresponding to the bearer for which packet duplicationmode is configured or activated when the packet duplication mode for thebearer is configured or activated; or a third establishment module,configured to establish the one or more secondary MAC entitiescorresponding to the bearer for which the packet duplication mode isconfigured or activated when the network side device configures oractivates packet duplication mode for a first UE of all UEs served bythe network side device.

Optionally, the network side device further includes: a first releasingmodule, configured to release the one or more secondary MAC entitiescorresponding to the bearer for which packet duplication mode isconfigured or activated when the packet duplication mode for the beareris deconfigured or deactivated; or a second releasing module, configuredto release the one or more secondary MAC entities corresponding to thebearer for which packet duplication mode is configured or activated whenthe packet duplication mode for a last bearer for which packetduplication mode is configured or activated of all bearers served by thenetwork side device is deconfigured or deactivated.

Optionally, the network side device further includes: a firstconfiguration module, configured to set semi-statically or dynamically amapping between the carriers and the master MAC entity and the one ormore secondary MAC entities, and transmitting the mapping to the UE whenthe packet duplication mode for the bearer is configured or activated.

Optionally, the network side device further includes: a secondconfiguration module, configured to set semi-statically or dynamically amapping between the logical channels and the master MAC entity and theone or more secondary MAC entities or a mapping between the logicalchannels and the carriers, and transmitting the mapping to the UE whenthe packet duplication mode for the bearer is configured or activated.

Optionally, both the master MAC entity and the one or more secondary MACentities are configured to bear a logical channel corresponding to abearer for which packet duplication mode is not configured or activatedand logical channels corresponding to a bearer for which packetduplication mode is configured or activated.

Optionally, the network side device further includes: a transferringmodule, configured to automatically transfer the logical channelcorresponding to the bearer for which packet duplication mode is notconfigured or activated that is borne on the released one of the one ormore secondary MAC entities to be borne on the master MAC entity whenone of the one or more secondary MAC entities is released.

Optionally, the master MAC entity is configured to bear a logicalchannel corresponding to a bearer for which packet duplication mode isnot configured or activated and logical channels corresponding to abearer for which packet duplication mode is configured or activated; andthe one or more secondary MAC entities are configured to only bearlogical channels corresponding to a bearer for which packet duplicationmode is configured or activated.

Optionally, the network side device further includes: a schedulingmodule, configured to receive buffer sizes, reported by the UE, of thelogical channels or logical channel groups corresponding to the masterMAC entity and the one or more secondary MAC entities of the UE, andperform uplink resource scheduling based on the buffer sizes of thelogical channels or logical channel groups corresponding to the masterMAC entity and the one or more secondary MAC entities of the UE.

Optionally, the network side device further includes: a UE capabilityreception module, configured to receive a UE capability transmitted bythe UE, wherein the UE capability carries capability indicationinformation indicating that the bearer using packet duplication mode issupported.

This disclosure further provides a computer readable storage mediumstoring therein a computer program, wherein the computer program isconfigured to be executed by a processor, to implement steps of themethods for transmitting data described above.

This disclosure further provides a UE, including a processor and amemory, wherein the processor is configured to read and execute aprogram stored in the memory to implement steps of the method fortransmitting data applied to the UE described above.

This disclosure further provides a network side device, including aprocessor and a memory, wherein the processor is configured to read andexecute a program stored in the memory to implement steps of the methodfor transmitting data applied to the network side device describedabove.

The aforementioned technical solutions of this disclosure havebeneficial effects as follows: by introducing MAC entities equal inquantity to the logical channels corresponding to the bearer for whichpacket duplication mode is enabled, it is guaranteed that each of thelogical channels corresponding to the bearer for which packetduplication mode is enabled is scheduled and transmitted through adifferent MAC entity, thereby due to multiplexing gain, transmissionquality following the duplication is ensured, and packet transmissionlatency is reduced.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram of the packet duplication model in arelated art;

FIG. 2 is a schematic diagram of a format of a MAC sub-header in arelated art;

FIG. 3 is a schematic diagram of a format of a short BSR MAC CE or atruncated BSR MAC CE in a related art;

FIG. 4 is a schematic diagram of a format of a long BSR MAC CE in arelated art;

FIG. 5 is a schematic flow diagram showing a method of transmitting dataapplied to UE side according to some embodiments of this disclosure;

FIG. 6 is a schematic flow diagram showing a method of transmitting dataapplied to a network side according to some embodiments of thisdisclosure;

FIG. 7 is a structural block diagram of a UE according to someembodiments of this disclosure;

FIG. 8 is a structural block diagram of a network side device accordingto some embodiments of this disclosure.

DETAILED DESCRIPTION

In order to make the objectives, the technical solutions and advantagesof embodiments of this disclosure clearer, the technical solutions ofembodiments of this disclosure will be described clearly and completelyin conjunction with drawings in the embodiments of the presentdisclosure hereinafter. Apparently, the described embodiments are merelya part of rather than all the embodiments of this disclosure. All otherembodiments obtained by a person ordinary skilled in the art based onthe embodiments of this disclosure fall within the protection scope ofthis disclosure.

Referring to FIG. 5, a schematic flow diagram showing a method oftransmitting data applied to a UE side according to some embodiments ofthis disclosure is illustrated, where the method includes the followingsteps.

Step S11: transmitting, by the UE, duplicated transmission data todifferent RLC entities respectively when a network side configures oractivates packet duplication mode for a bearer.

Step S12: transmitting, by one of the different RLC entities, thetransmission data through one of logical channels to a master MAC entityand transmitting, by each of the others of the different RLC entities,the transmission data through a different one of the logical channels toa different one of one or more secondary MAC entities.

Step S13: transmitting, by the master MAC entity and the one or moresecondary MAC entity, the transmission data to the network side throughdifferent carriers.

In some embodiments of this disclosure, by introducing MAC entitiesequal in quantity to the logical channels corresponding to the bearerfor which packet duplication mode is enabled, it is guaranteed that eachof the logical channels corresponding to the bearer for which packetduplication mode is enabled is scheduled and transmitted through adifferent MAC entity, thereby due to multiplexing gain, transmissionquality following the duplication is ensured, and packet transmissionlatency is reduced.

In some embodiments of this disclosure, the packet duplication mode maybe valid in the following two manners: valid upon configuration; andbeing configured first, then valid upon activation.

In some embodiments of this disclosure, duplication of transmission datamay be performed by the PDCP entity or a protocol layer on top of PDCPlayer.

In some embodiments of this disclosure, the bearer for which packetduplication mode is enabled corresponds to at least two logicalchannels, where each of the logical channels corresponds to one RLCentity and each of the logical channels corresponds to one MAC entity.

In some embodiments of this disclosure, the first MAC entity establishedby the UE is called master MAC entity and other MAC entities are calledsecondary MAC entities.

In some embodiments of this disclosure, the secondary MAC entities maybe established in one of the following conditions (but not limitedthereto).

1) The secondary MAC entities are established together with the masterMAC entity.

In some embodiments of this disclosure, in a UE supporting a bearer forwhich packet duplication mode is enabled, the secondary MAC entities andthe master MAC entity may be established and released together, and theUE always maintains the master MAC entity and the secondary MAC entitiessimultaneously, no matter whether packet duplication mode is configuredor activated for the bearer.

2) The UE establishes the secondary MAC entities corresponding to thebearer for which packet duplication mode is enabled when the networkside configures or activates packet duplication mode for the bearer.

In the case that the secondary MAC entities are established in thecondition 2), the secondary MAC entities may be released in thefollowing condition (but not limited thereto): when the network sidedeconfigures or deactivates packet duplication mode for the bearer, theUE releases the secondary MAC entities corresponding to the bearer forwhich packet duplication mode is enabled.

In some embodiments of this disclosure, in a UE supporting a bearer forwhich packet duplication mode is enabled, the master MAC entity isalways maintained by the UE, however the secondary MAC entities areestablished or released according to whether packet duplication mode isconfigured or activated for the bearer.

In some embodiments of this disclosure, the UE and the network side arekept in conformity in regard to the establishment or release mode of thesecondary MAC entities, where the conformity may be maintained throughprotocol specification or signaling notification.

In some embodiments of this disclosure, a mapping between the carriersand the master MAC entity and the secondary MAC entities may beconfigured by the network side semi-statically or dynamically andtransmitted to the UE.

Optionally, in the case that the network side configures semi-staticallythe mapping between the carriers and the master MAC entity and thesecondary MAC entities and transmits the mapping to the UE, the mappingmay be transmitted to the UE through Radio Resource Control (RRC)signaling semi-statically.

Optionally, in the case that the network side configures dynamically themapping between the carriers and the master MAC entity and the secondaryMAC entities and transmits the mapping to the UE, the mapping may betransmitted to the UE through L1/L2 signaling dynamically.

That is, in some embodiments of this disclosure, prior to the UEtransmitting the duplicated transmission data to the different RLCentities respectively, the method further includes: receiving themapping between the carriers and the master MAC entity and the secondaryMAC entities that is configured by the network side semi-statically ordynamically.

In some embodiments of this disclosure, a mapping between the logicalchannels and the master MAC entity and the secondary MAC entities or amapping between the logical channels and the carriers may be configuredby the network side semi-statically or dynamically and transmitted tothe UE.

Optionally, in the case that the network side configures semi-staticallythe mapping between the logical channels and the master MAC entity andthe secondary MAC entities or the mapping between the logical channelsand the carriers and transmits the mapping to the UE, the mapping may betransmitted to the UE through RRC signaling semi-statically.

Optionally, in the case that the network side configures dynamically themapping between the logical channels and the master MAC entity and thesecondary MAC entities or the mapping between the logical channels andthe carriers and transmits the mapping to the UE, the mapping may betransmitted to the UE through L1/L2 signaling dynamically.

That is, in some embodiments of this disclosure, prior to the UEtransmitting the duplicated transmission data to the different RLCentities respectively, the method further includes: receiving themapping between the logical channels and the master MAC entity and thesecondary MAC entities or the mapping between the logical channels andthe carriers that is configured by the network side semi-statically ordynamically.

In some embodiments of this disclosure, the master MAC entity and thesecondary MAC entities may be used according to one of the followingrules (but not limited thereto).

1) Both the master MAC entity and the secondary MAC entities areconfigured to bear a logical channel corresponding to a bearer for whichpacket duplication mode is not configured or activated and logicalchannels corresponding to a bearer for which packet duplication mode isconfigured or activated.

In this case, optionally, when one of the secondary MAC entities isreleased, the logical channel corresponding to the bearer for whichpacket duplication mode is not configured or activated that is borne onthe released MAC entity is automatically transferred to be borne on themaster MAC entity, with no additional signaling configuration required.

2) The master MAC entity is configured to bear a logical channelcorresponding to a bearer for which packet duplication mode is notconfigured or activated and logical channels corresponding to a bearerfor which packet duplication mode is configured or activated; and thesecondary MAC entities are configured to only bear logical channelscorresponding to a bearer for which packet duplication mode isconfigured or activated.

In some embodiments of this disclosure, prior to transmitting thetransmission data to the network side device, the UE may perform a BSRreporting. Hereinafter, how the UE performs the BSR in some embodimentsof this disclosure is detailed.

First, the BSR mechanism in the Long Term Evolution (LTE) system isbriefly introduced.

All LTE systems are based on scheduling, where eNodeB (eNB) allocates toUE time-frequency resources required for data transmission, and UEconducts Downlink (DL) data reception or Uplink (UL) data transmissionbased on the scheduling command of eNB. The UL data transmission isscheduled by eNB, where an eNB scheduler determines the UL resourceallocation and then informs UE of the allocation result through ULgrant. The eNB scheduler allocates the UL resources based on the UL dataamount to be transmitted by the UE, i.e., the UE buffer state. Since thebuffer is located at the UE side, in order to make the informationavailable to the eNB, UE must perform a BSR reporting toward eNB. TheBSR mechanism of LTE Rel-11 and previous releases is as follows.

1. Granularity of BSR

BSR of LTE system is based on Logical Channel Group (LCG). Four LCGs aredefined in total. LCG ID corresponding to the bearer/logical channel isconfigured during bearer establishment procedure.

2. RRC Layer BSR Related Parameter Configuration

In LTE system, the RRC layer parameters directed to BSR configurationinclude the following timers, both of which are configured andmaintained based on UE: 1) retxBSR-Timer: the timer prohibits BSRreporting; 2) periodicBSR-Timer: the timer controls the periodic BSRreporting.

3. Categories of BSRs and Trigger Mechanism Thereof

1) Regular BSR: (1) triggered if data with higher priority than thosewaiting in the buffer arrive or data arrive at empty buffer; (2)triggered when the retxBSR-Timer expires and there are data in thebuffer.

2) Periodic BSR: triggered when the periodicBSR-Timer expires.

3) Padding BSR: may be triggered if there is still resource availableafter resources are allocated for to-be-transmitted data during MAC PDUconstruction by UE.

4. Principle of BSR Reporting

For Regular BSR and Periodic BSR, if more than one LCG has dataavailable, the UE reports a long BSR, else reports a short BSR.

For Padding BSR, if the number of padding bits is equal to or largerthan (short BSR+MAC sub-header) but smaller than (long BSR+MACsub-header), if more than one LCG has data available, the UE reports atruncated BSR, else reports a short BSR; if the number of padding bitsis equal to or larger than (long BSR+MAC sub-header), reports a longBSR.

When a BSR is triggered, both Periodic BSR and Padding BSR may bereported only if there are UL resources available; for Regular BSR, ifthere is no UL resource available, a Scheduling Request is triggered torequest eNB to allocate UL resources for UE.

After eNB has allocated UL resources to UE, if the resources are justenough for the transmission of all UL data, BSR is not transmitted,instead the UL data are transmitted directly; if the resources are notenough for the transmission of all UL data, Regular BSR or Periodic BSRare reported preferentially, then eNB performs transmission schedulingsubsequently based on the UL data amount to be transmitted by UEreported in the BSR.

One MAC PDU contains at most one BSR. The priority of BSRs is: RegularBSR=Periodic BSR>Padding BSR. If multiple BSRs are triggered at the sametime, only the BSR with the highest priority is reported. Since RegularBSR and Periodic BSR are the same in terms of report content (bothcontain data amount information of all data available for transmissionin UE buffer) and report format, the choice between Regular BSR andPeriodic BSR is arbitrary. During the construction of MAC PDU at MAClayer, these two types of MAC Control Elements (CE) are placedpreferentially, and then MAC Service Data Unit (SDU) is placed.

Padding BSR has a lower priority than data. Padding BSR andRegular/Periodic BSR may be reported in different MAC PDUs in the samesub-frame.

5. Procedure Following the BSR Reporting

As long as a BSR is triggered and can be reported, the periodicBSR-Timerand retxBSR-Timer are started or restarted. However, it is noted, fortruncated BSR, the periodicBSR-Timer may not be started or restarted,and only the retxBSR-Timer is started or restarted.

6. BSR Format

BSR is reported in the form of MAC CE, which may be divided into MACsub-header and MAC CE. BSR MAC CE has two formats: long BSR and shortBSR, where truncated BSR has the same format as the short BSR.

The formats of MAC sub-header and BSR MAC CE in LTE system are as shownin FIG. 2 to FIG. 4.

The fields therein are defined as follows.

Logical Channel ID (LCID): this field indicates logical channel ID ofcorresponding load, where long BSR, short BSR and truncated BSR each hasone LCID.

E: extended bit, used to indicate the next byte is MAC sub-header or MACload.

R: reserved bit.

LCG ID: logical channel group ID. Four logical channel groups aredefined for BSR in LTE system.

Buffer Size: amount of data of corresponding logical channel group inthe buffer.

As far as BSR reporting is concerned, the distinction between LTE R10/11and LTE R8/9 consists in that, in the R10/11, a new BS table isintroduced since carrier aggregation is supported and as a result peakrate is increased. When a UE supporting R10/11 reports a BSR, whetherthe new BS table is utilized is configured by eNB through RRC signaling.Whether the BS table in LTE R8/9 or the BS table in LTE R10/11 isquantized in 64 levels, i.e., corresponding quantized value may berepresented by 6 bits. As a result, the field buffer size of each LCG inthe above BSR MAC CE format consists of 6 bits.

In some embodiments of this disclosure, the method of transmitting datafurther includes the followings steps.

1) Determining whether to trigger a BSR.

2) In the case that it is determined the BSR is to be triggered,reporting to the network side buffer sizes of the logical channels orlogical channel groups corresponding to the master MAC entity and theone or more secondary MAC entities.

In some embodiments of this disclosure, determining whether to triggerthe BSR may be performed in the following two ways (but not limitedthereto).

One way of determining whether to trigger the BSR is: determiningwhether to trigger the BSR based on the UE.

The trigger mechanism of determining whether to trigger the BSR based onthe UE may be the same as the trigger mechanism of LTE system explainedabove.

That is, for Regular BSR, the trigger mechanism is: (1) triggered ifdata with higher priority than those waiting in the buffer arrive ordata arrive at empty buffer; (2) triggered when the retxBSR-Timerexpires and there are data in the buffer. For Periodic BSR, the triggermechanism is: triggered when the periodicBSR-Timer expires. For PaddingBSR, the trigger mechanism is: may be triggered if there is stillresource available after resources are allocated for to-be-transmitteddata during MAC PDU construction by UE.

In some embodiments of this disclosure, in BSR reporting, BSR MAC CE maybe configured by the following two forms.

1) Reporting to the network side the buffer sizes of the logicalchannels or logical channel groups corresponding to the master MACentity and the secondary MAC entities through one BSR MAC CE, where acarrier corresponding to any one MAC entity of the master MAC entity andthe secondary MAC entities is used in the reporting.

In the case that there is a repetition of ID among the logical channelsor logical channel groups corresponding to different MAC entities,identification information may be added in the BSR MAC CE to identify acorrespondence between the logical channels or logical channel groupsand the MAC entities.

2) Reporting to the network side the buffer sizes of the logicalchannels or logical channel groups corresponding to the master MACentity and the secondary MAC entities through a plurality of independentBSR MAC CEs in one MAC PDU, where a carrier corresponding to any one MACentity of the master MAC entity and the secondary MAC entities is usedin the reporting.

In the case that there is a repetition of ID among the logical channelsor logical channel groups corresponding to different MAC entities,identification information may be added in the BSR MAC CE to identify acorrespondence between the logical channels or logical channel groupsand the MAC entities.

Another way of determining whether to trigger the BSR is: determiningwhether to trigger the BSR based on a MAC entity.

The trigger mechanism in the determining whether to trigger the BSRbased on the MAC entity may be the same as the trigger mechanism of LTEsystem explained above, thus a repeated description thereof is omittedherein.

In some embodiments of this disclosure, in BSR reporting, BSR MAC CE maybe configured by the following form.

Reporting to the network side the buffer sizes of the logical channelsor logical channel groups corresponding to the master MAC entity and thesecondary MAC entities by using a carrier corresponding to the MACentity or a carrier corresponding to other MAC entity.

In the case that a carrier used in BSR MAC CE transmission is notlimited and there is a repetition of ID among the logical channels orlogical channel groups corresponding to different MAC entities,identification information is added in the BSR MAC CE to identify acorrespondence between the logical channels or logical channel groupsand the MAC entities.

In some embodiments of this disclosure, in order to make the networkside aware of whether the bearer using packet duplication mode issupported by UE, optionally, prior to the UE transmitting the duplicatedtransmission data to the different RLC entities respectively, the methodfurther includes: transmitting a UE capability to the network side,where the UE capability contains capability indication informationindicating that the bearer using packet duplication mode is supported.

In other words, only the UE supporting the bearer using packetduplication mode may transmit data using the method for transmittingdata described above.

In some embodiments of this disclosure, the method of transmitting datais applicable to data transmission using the packet duplication mode inCarrier Aggregation scenario.

Referring to FIG. 6, a schematic flow diagram of a method oftransmitting data applied to a network side according to someembodiments of this disclosure is illustrated, where the method includesthe following steps.

Step S21: receiving, by a master MAC entity and one or more secondaryMAC entities of a network side device, duplicated transmission datatransmitted by a UE through different carriers when a packet duplicationmode is configured or activated for a bearer.

Step S22: transmitting, by the master MAC entity and the one or moresecondary MAC entities, the transmission data to different RLC entitiesthrough different logical channels.

Step S23: transmitting, by the RLC entities, received transmission datato a PDCP entity.

In some embodiments of this disclosure, by introducing MAC entitiesequal in quantity to the logical channels corresponding to the bearerfor which packet duplication mode is enabled, it is guaranteed that eachof the logical channels corresponding to the bearer for which packetduplication mode is enabled is scheduled and transmitted through adifferent MAC entity, thereby due to multiplexing gain, transmissionquality following the duplication is ensured, and packet transmissionlatency is reduced.

In some embodiments of this disclosure, the bearer for which packetduplication mode is enabled corresponds to at least two logicalchannels, where each of the logical channels corresponds to one RLCentity and each of the logical channels corresponds to one MAC entity.

In some embodiments of this disclosure, duplication of transmission datamay be performed by the PDCP entity or a protocol layer on top of PDCPlayer.

In some embodiments of this disclosure, the first MAC entity establishedby the UE is called master MAC entity and other MAC entities are calledsecondary MAC entities.

In some embodiments of this disclosure, the secondary MAC entities maybe established in one of the following conditions (but not limitedthereto).

1) The secondary MAC entities are established together with the masterMAC entity.

2) The secondary MAC entities corresponding to the bearer for whichpacket duplication mode is enabled are established when the network sideconfigures or activates packet duplication mode for the bearer.

In the case that the secondary MAC entities are established in thecondition 2), the secondary MAC entities may be released in thefollowing condition (but not limited thereto): when the network sidedeconfigures or deactivates packet duplication mode for the bearer, theUE releases the secondary MAC entities corresponding to the bearer forwhich packet duplication mode is enabled.

3) The secondary MAC entities corresponding to the bearer for whichpacket duplication mode is enabled are established when the network sidedevice configures or activates packet duplication mo for a first UE ofall UEs served by the network side device.

In the case that the secondary MAC entities are established in thecondition 3), the secondary MAC entities may be released in thefollowing condition (but not limited thereto): when packet duplicationmode for a last bearer for which packet duplication mode is enabled ofall bearers served by the network side device is deconfigured ordeactivated, releasing the secondary MAC entities corresponding to thebearer for which packet duplication mode is enabled.

In some embodiments of this disclosure, the UE and the network side arekept in conformity in regard to the establishment or release mode of thesecondary MAC entities, where the conformity may be maintained throughprotocol specification or signaling notification.

In some embodiments of this disclosure, the method of transmitting datafurther includes: in the case that packet duplication mode for thebearer is configured or activated, configuring semi-statically ordynamically a mapping between the carriers and the master MAC entity andthe secondary MAC entities, and transmitting the mapping to the UE.

Optionally, in the case that the network side configures semi-staticallythe mapping between the carriers and the master MAC entity and thesecondary MAC entities and transmits the mapping to the UE, the mappingmay be transmitted to the UE through RRC signaling semi-statically.

Optionally, in the case that the network side configures dynamically themapping between the carriers and the master MAC entity and the secondaryMAC entities and transmits the mapping to the UE, the mapping may betransmitted to the UE through L1/L2 signaling dynamically.

In some embodiments of this disclosure, the method for transmitting datafurther includes: in the case that packet duplication mode for thebearer is configured or activated, configuring semi-statically ordynamically a mapping between the logical channels and the master MACentity and the secondary MAC entities or a mapping between the logicalchannels and the carriers, and transmitting the mapping to the UE.

Optionally, in the case that the network side configures semi-staticallythe mapping between the logical channels and the master MAC entity andthe secondary MAC entities or the mapping between the logical channelsand the carriers and transmits the mapping to the UE, the mapping may betransmitted to the UE through RRC signaling semi-statically.

Optionally, in the case that the network side configures dynamically themapping between the logical channels and the master MAC entity and thesecondary MAC entities or the mapping between the logical channels andthe carriers and transmits the mapping to the UE, the mapping may betransmitted to the UE through L1/L2 signaling dynamically.

In some embodiments of this disclosure, the master MAC entity and thesecondary MAC entities may be used according to one of the followingrules (but not limited thereto).

1) Both the master MAC entity and the secondary MAC entities areconfigured to bear a logical channel corresponding to a bearer for whichpacket duplication mode is not configured or activated and logicalchannels corresponding to a bearer for which packet duplication mode isconfigured or activated.

In this case, optionally, when one of the secondary MAC entities isreleased, the logical channel corresponding to the bearer for whichpacket duplication mode is not configured or activated that is borne onthe released MAC entity is automatically transferred to be borne on themaster MAC entity, with no additional signaling configuration required.

2) The master MAC entity is configured to bear a logical channelcorresponding to a bearer for which packet duplication mode is notconfigured or activated and logical channels corresponding to a bearerfor which packet duplication mode is configured or activated; and thesecondary MAC entities are configured to only bear logical channelscorresponding to a bearer for which packet duplication mode isconfigured or activated.

In some embodiments of this disclosure, prior to transmitting thetransmission data to the network side device, the UE may perform a BSRreporting. That is, in some embodiments of this disclosure, the methodof transmitting data may further include: receiving buffer sizes,reported by the UE, of the logical channels or logical channel groupscorresponding to the master MAC entity and the secondary MAC entities ofthe UE, and performing uplink resource scheduling based on the buffersizes of the logical channels or logical channel groups corresponding tothe master MAC entity and the secondary MAC entities of the UE.

In some embodiments of this disclosure, prior to the network sideconfiguring or activating packet duplication mode for the bearer, themethod may further include: receiving a UE capability transmitted by theUE, where the UE capability contains capability indication informationindicating that the bearer using packet duplication mode is supported.

That is, optionally, the network side won't configure or activate packetduplication mode for the bearer between the network side and the UE,until the capability indication information, transmitted by the UE,indicating that the bearer using packet duplication mode is supported isreceived by the network side.

Based on the same inventive concept, this disclosure further provides aUE.

Referring to FIG. 7, a structural block diagram of a UE according tosome embodiments of this disclosure is illustrated, where the UEincludes: a first transmission module, configured to transmit duplicatedtransmission data to different RLC entities respectively when a networkside configures or activates packet duplication mode for a bearer; asecond transmission module, configured to trigger one of the differentRLC entities to transmit the transmission data through one of logicalchannels to a master MAC entity and trigger the others of the differentRLC entities to transmit the transmission data through different logicalchannels to different secondary MAC entities; and a third transmissionmodule, configured to trigger the master MAC entity and the one or moresecondary MAC entities to transmit the transmission data throughdifferent carriers to the network side.

In some embodiments of this disclosure, by introducing MAC entitiesequal in quantity to the logical channels corresponding to the bearerfor which packet duplication mode is enabled, it is guaranteed that eachof the logical channels corresponding to the bearer for which packetduplication mode is enabled is scheduled and transmitted through adifferent MAC entity, thereby due to multiplexing gain, transmissionquality following the duplication is ensured, and packet transmissionlatency is reduced.

In some embodiments of this disclosure, the bearer for which packetduplication mode is enabled corresponds to at least two logicalchannels, where each of the logical channels corresponds to one RLCentity and each of the logical channels corresponds to one MAC entity.

In some embodiments of this disclosure, the first MAC entity establishedby the UE may be called master MAC entity and other MAC entities may becalled secondary MAC entities.

In some embodiments of this disclosure, the secondary MAC entities maybe established using one of the following two modules of UE (but notlimited thereto).

A first establishment module is configured to establish the one or moresecondary MAC entities together with the master MAC entity.

A second establishment module is configured to, in the case that thenetwork side configures or activates packet duplication mode for thebearer, establish the one or more secondary MAC entities correspondingto the bearer for which packet duplication mode is enabled.

In the case that the secondary MAC entities are established by thesecond establishment module, the UE may further include: a releasingmodule, configured to, in the case that the network side deconfigures ordeactivates packet duplication mode for the bearer, release thesecondary MAC entities corresponding to the bearer for which packetduplication mode is enabled.

In order to acquire a mapping between the carriers and the master MACentity and the one or more secondary MAC entities, the UE may furtherinclude: a first reception module, configured to receive the mappingbetween the carriers and the master MAC entity and the one or moresecondary MAC entities that is configured by the network sidesemi-statically or dynamically.

In order to acquire a mapping between the logical channels and themaster MAC entity and the one or more secondary MAC entities or amapping between the logical channels and the carriers, the UE mayfurther include: a second reception module, configured to receive themapping between the logical channels and the master MAC entity and theone or more secondary MAC entities or the mapping between the logicalchannels and the carriers that is configured by the network sidesemi-statically or dynamically.

In some embodiments of this disclosure, the master MAC entity and thesecondary MAC entities may be used according to one of the followingrules (but not limited thereto).

1) Both the master MAC entity and the secondary MAC entities areconfigured to bear a logical channel corresponding to a bearer for whichpacket duplication mode is not configured or activated and logicalchannels corresponding to a bearer for which packet duplication mode isconfigured or activated.

In this case, optionally, the UE may further include: a transferringmodule, configured to, in the case that one of the one or more secondaryMAC entities is released, automatically transfer the logical channelcorresponding to the bearer for which packet duplication mode is notconfigured or activated that is borne on the released secondary MACentity to be borne on the master MAC entity.

2) The master MAC entity is configured to bear a logical channelcorresponding to a bearer for which packet duplication mode is notconfigured or activated and logical channels corresponding to a bearerfor which packet duplication mode is configured or activated; and theone or more secondary MAC entities are configured to only bear logicalchannels corresponding to a bearer for which packet duplication mode isconfigured or activated.

In some embodiments of this disclosure, prior to transmitting thetransmission data to the network side device, the UE may perform a BSRreporting first, where the UE may further include: a determinationmodule, configured to determine whether to trigger a BSR; and areporting module, configured to, in the case that it is determined theBSR is to be triggered, report to the network side buffer sizes of thelogical channels or logical channel groups corresponding to the masterMAC entity and the one or more secondary MAC entities.

In some embodiments of this disclosure, the determination module maydetermine whether to trigger the BSR based on the UE, where thereporting module may be further configured to report to the network sidethe buffer sizes of the logical channels or logical channel groupscorresponding to the master MAC entity and the one or more secondary MACentities by using a carrier corresponding to any one MAC entity of themaster MAC entity and the one or more secondary MAC entities.

Further, the reporting module may be configured to report to the networkside the buffer sizes of the logical channels or logical channel groupscorresponding to the master MAC entity and the one or more secondary MACentities through one BSR MAC CE.

Alternatively, the reporting module may be further configured to reportto the network side the buffer sizes of the logical channels or logicalchannel groups corresponding to the master MAC entity and the one ormore secondary MAC entities through a plurality of independent BSR MACCEs in one MAC PDU.

In some embodiments of this disclosure, the determination module maydetermine whether to trigger the BSR based on a MAC entity, where thereporting module may be further configured to report to the network sidethe buffer sizes of the logical channels or logical channel groupscorresponding to the master MAC entity and the one or more secondary MACentities by using a carrier corresponding to the MAC entity or a carriercorresponding to other MAC entity.

Further, the reporting module is configured to, in the case that acarrier used in BSR MAC CE transmission is not limited and there is arepetition of ID among the logical channels or logical channel groupscorresponding to different MAC entities, add identification informationin the BSR MAC CE to identify a correspondence between the logicalchannels or logical channel groups and the MAC entities.

In order to make the network side aware of whether the bearer usingpacket duplication mode is supported by UE, optionally, in someembodiments of this disclosure, the UE may further include: a UEcapability transmission module, configured to transmit a UE capabilityto the network side, where the UE capability contains capabilityindication information indicating that the bearer using packetduplication mode is supported.

Based on the same inventive concept, some embodiments of this disclosurefurther provide a network side device.

Referring to FIG. 8, a structural block diagram of a network side deviceaccording to some embodiments of this disclosure is illustrated, wherethe network side device includes: a reception module, configured totrigger a master MAC entity and one or more secondary MAC entities torespectively receive duplicated transmission data transmitted by a UEthrough different carriers when packet duplication mode for a bearer isconfigured or activated; a first transmission module, configured totrigger the master MAC entity and the one or more secondary MAC entitiesto transmit the transmission data to different RLC entities throughdifferent logical channels; and a second transmission module, configuredto trigger the RLC entities to transmit received transmission data to aPDCP entity.

In some embodiments of this disclosure, the bearer for which packetduplication mode is enabled corresponds to at least two logicalchannels, where each of the logical channels corresponds to one RLCentity and each of the logical channels corresponds to one MAC entity.

In some embodiments of this disclosure, duplication of transmission datamay be performed by the PDCP entity or a protocol layer on top of PDCPlayer.

That is, the UE may further include: a bearer duplication module,configured to trigger the PDCP entity or a protocol layer on top of PDCPlayer to perform bearer duplication.

In some embodiments of this disclosure, the secondary MAC entities maybe established using one of the following three modules of the networkside device.

A first establishment module is configured to establish the one or moresecondary MAC entities together with the master MAC entity.

A second establishment module is configured to establish the one or moresecondary MAC entities corresponding to the bearer for which packetduplication mode is enabled when the packet duplication mode for thebearer is configured or activated.

A third establishment module is configured to establish the one or moresecondary MAC entities corresponding to the bearer for which packetduplication mode is enabled when the packet duplication mode for a firstUE of all UEs served by the network side device is configured oractivated.

In the case that the one or more secondary MAC entities are establishedby the second establishment module, the network side device may furtherinclude: a first releasing module, configured to, in the case thatpacket duplication mode for the bearer is deconfigured or deactivated,release the one or more secondary MAC entities corresponding to thebearer for which packet duplication mode is configured or activated.

In the case that the one or more secondary MAC entities are establishedby the third establishment module, the network side device may furtherinclude: a second releasing module, configured to, in the case thatpacket duplication mode for a last bearer for which packet duplicationmode is configured or activated of all bearers served by the networkside device is deconfigured or deactivated, release the one or moresecondary MAC entities corresponding to the bearer for which packetduplication mode is enabled.

In order to inform a UE of a mapping between the carriers and the masterMAC entity and the one or more secondary MAC entities, the network sidedevice may further include: a first configuration module, configured to,in the case that packet duplication mode for the bearer is configured oractivated, configure semi-statically or dynamically the mapping betweenthe carriers and the master MAC entity and the one or more secondary MACentities, and transmit the mapping to the UE.

In order to inform a UE of a mapping between the logical channels andthe master MAC entity and the one or more secondary MAC entities or amapping between the logical channels and the carriers, the network sidedevice may further include: a second configuration module, configuredto, in the case that packet duplication mode for the bearer isconfigured or activated, configure semi-statically or dynamically themapping between the logical channels and the master MAC entity and theone or more secondary MAC entities or the mapping between the logicalchannels and the carriers, and transmit the mapping to the UE.

In some embodiments of this disclosure, the master MAC entity and thesecondary MAC entities may be used according to one of the followingrules (but not limited thereto).

1) Both the master MAC entity and the secondary MAC entities areconfigured to bear a logical channel corresponding to a bearer for whichpacket duplication mode is not configured or activated and logicalchannels corresponding to a bearer for which packet duplication mode isconfigured or activated.

In this case, optionally, the network side device may further include: atransferring module, configured to, in the case that one of the one ormore secondary MAC entities is released, automatically transfer thelogical channel corresponding to the bearer for which packet duplicationmode is not configured or activated that is borne on the releasedsecondary MAC entity to be borne on the master MAC entity.

2) The master MAC entity is configured to bear a logical channelcorresponding to a bearer for which packet duplication mode is notconfigured or activated and logical channels corresponding to a bearerfor which packet duplication mode is configured or activated; and theone or more secondary MAC entities are configured to only bear logicalchannels corresponding to a bearer for which packet duplication mode isconfigured or activated.

In some embodiments of this disclosure, prior to transmitting thetransmission data to the network side device, the UE may perform a BSRreporting first, where the network side device may further include: ascheduling module, configured to receive buffer sizes, reported by theUE, of the logical channels or logical channel groups corresponding tothe master MAC entity and the one or more secondary MAC entities of theUE, and perform uplink resource scheduling based on the buffer sizes ofthe logical channels or logical channel groups corresponding to themaster MAC entity and the one or more secondary MAC entities of the UE.

In order to make the network side aware of whether the bearer usingpacket duplication mode is supported by UE, optionally, a UE supportinga bearer for which packet duplication mode is enabled may transmit tothe network side a UE capability containing capability indicationinformation indicating that the bearer using packet duplication mode issupported; correspondingly, the network side device may further include:a UE capability reception module, configured to receive a UE capabilitytransmitted by the UE, where the UE capability contains capabilityindication information indicating that the bearer using packetduplication mode is supported.

Some embodiments of this disclosure further provide an apparatus forprocessing data, including: a processor and a memory connected to theprocessor through a bus interface, where the memory is configured tostore program and data being used by the processor in operation, and theprocessor is configured to call and execute the program and data storedin the memory to implement the following functional modules or units: afirst transmission module, configured to transmit duplicatedtransmission data to different RLC entities respectively when a networkside configures or activates packet duplication mode for a bearer; asecond transmission module, configured to trigger one of the differentRLC entities to transmit the transmission data through one of logicalchannels to a master MAC entity and trigger each of the others of thedifferent RLC entities to transmit the transmission data through adifferent logical channel to a different secondary MAC entity; and athird transmission module, configured to trigger the master MAC entityand the secondary MAC entity to transmit the transmission data throughdifferent carriers to the network side.

Some embodiments of this disclosure further provide an apparatus forprocessing data, including: a processor and a memory connected to theprocessor through a bus interface, where the memory is configured tostore program and data being used by the processor in operation, and theprocessor is configured to call and execute the program and data storedin the memory to implement the following functional modules or units: areception module, configured to trigger a master MAC entity and one ormore secondary MAC entities to respectively receive duplicatedtransmission data transmitted by a UE through different carriers whenpacket duplication mode for a bearer is configured or activated; a firsttransmission module, configured to trigger the master MAC entity and theone or more secondary MAC entities to transmit the transmission data todifferent RLC entities through different logical channels; and a secondtransmission module, configured to trigger the RLC entities to transmitreceived transmission data to a PDCP entity.

It is noted, the apparatuses provided in some embodiments of thisdisclosure are capable of implementing the corresponding methods oftransmitting data provided in the abovementioned method embodiments,thus all embodiments of the methods of transmitting data provided in theabovementioned method embodiments may be applied correspondingly to thetwo apparatus embodiments described above and achieve the same orsimilar advantageous effects.

Some embodiments of this disclosure further provide a computer readablestorage medium storing therein a computer program, wherein the computerprogram is configured to be executed by a processor, to implement stepsof the method of transmitting data described in any one ofabovementioned embodiments.

The computer readable storage medium includes permanent andnon-permanent, removable and non-removable media, and may achieveinformation storage by any means or techniques. Information may becomputer readable instruction, data structure, program module or otherdata. Computer storage medium may, for example, include, but not limitedto: Phase Change Random Access Memory (PRAM), Static Random AccessMemory (SRAM), Dynamic Random Access Memory (DRAM), other types ofRandom Access Memories (RAM), Read Only Memory (ROM), ElectricallyErasable Programmable Read Only Memory (EEPROM), FLASH or other memorytechnologies, Compact Disc Read Only Memory (CD-ROM), Digital VersatileDisc (DVD) or other optical storages, cassette tape, magnetic tape,magnetic disk or other magnetic storage device or any othernon-transmitting medium, which is configured to store informationaccessible by a computing device. According to the definition herein,the computer readable medium does not include transitory media, such asmodulated data signals and carriers.

Some embodiments of this disclosure further provide a UE, including aprocessor and a memory, where the processor is configured to read andexecute a program stored in the memory to implement steps of theabovementioned method of transmitting data applied to the UE side.

Some embodiments of this disclosure further provide a network sidedevice, including a processor and a memory, where the processor isconfigured to read and execute a program stored in the memory toimplement steps of the abovementioned method for transmitting dataapplied to the network side.

In the embodiments provided in this disclosure, it should be understoodthat the disclosed method and apparatus may be implemented in othermanners. For example, the described apparatus embodiment is merelyexemplary. For example, the unit division is merely logical functiondivision and may be other division in actual implementation. Forexample, a plurality of units or components may be combined orintegrated into another system, or some features may be neglected or notperformed. In addition, the displayed or discussed mutual couplings ordirect couplings or communication connections may be implemented throughsome interfaces. The indirect couplings or communication connectionsbetween the apparatuses or units may be implemented in electrical,mechanical, or other forms.

In addition, various functional units in the embodiments of thisdisclosure may be integrated into one processing unit, or each of theunits may exist alone physically. Alternatively, two or more thesefunctional units may be integrated into one unit. The above integratedunit may be implemented in form of hardware, or may be implemented inform of a combination of hardware and software functional unit.

The integrated units implemented in form of software functional unit maybe stored in a computer-readable storage medium. The software functionalunit is stored in a storage medium, and includes several instructionsfor instructing a computer device (which may be a personal computer, aserver, or a network device) to perform a part of the steps of thetransmitting and receiving methods described in the embodiments of thisdisclosure. The foregoing storage medium includes any medium that canstore program code, such as a Universal Serial Bus (USB) flash drive, aremovable hard disk, a Read-Only Memory (ROM), a Random Access Memory(RAM), a magnetic disk, or an optical disc.

The above descriptions merely describe some implementations of thisdisclosure. It is appreciated, modifications and improvements may bemade by a person of ordinary skill in the art without departing from theprinciple of this disclosure, and these modifications and improvementsshall fall within the scope of this disclosure.

What is claimed is:
 1. A method of transmitting data applied to a userequipment (UE), comprising: transmitting, by the UE, duplicatedtransmission data to different radio link control (RLC) entitiesrespectively when a network side configures or activates a packetduplication mode for a bearer; transmitting, by one of the different RLCentities, the transmission data through one of logical channels to amaster medium access control (MAC) entity and transmitting, by each ofthe others of the different RLC entities, the transmission data througha different one of the logical channels to a different one of one ormore secondary MAC entities; and transmitting, by the master MAC entityand the one or more secondary MAC entities, the transmission data to thenetwork side through different carriers.
 2. The method according toclaim 1, wherein each of the logical channels corresponds to one RLCentity and each of the logical channels corresponds to one MAC entity.3. The method according to claim 1, wherein the one or more secondaryMAC entities are established together with the master MAC entity.
 4. Themethod according to claim 1, further comprising: establishing, the UE,the one or more secondary MAC entities corresponding to the bearer forwhich packet duplication mode is configured or activated when thenetwork side configures or activates the packet duplication mode for thebearer.
 5. The method according to claim 4, further comprising:releasing, by the UE, the one or more secondary MAC entitiescorresponding to the bearer for which packet duplication mode isconfigured or activated when the network side deconfigures ordeactivates the packet duplication mode for the bearer.
 6. The methodaccording to claim 1, wherein prior to the transmitting, by the UE, theduplicated transmission data to the different RLC entities respectively,the method further comprises: receiving a mapping between the carriersand the master MAC entity and the one or more secondary MAC entitiesthat is configured by the network side semi-statically or dynamically;or receiving a mapping between the logical channels and the master MACentity and the one or more secondary MAC entities or a mapping betweenthe logical channels and the carriers that is configured by the networkside semi-statically or dynamically.
 7. (canceled)
 8. The methodaccording to claim 1, wherein both the master MAC entity and the one ormore secondary MAC entities are configured to bear a logical channelcorresponding to a bearer for which packet duplication mode is notconfigured or activated and logical channels corresponding to a bearerfor which packet duplication mode is configured or activated.
 9. Themethod according to claim 8, wherein when one of the one or moresecondary MAC entities is released, the logical channel corresponding tothe bearer for which packet duplication mode is not configured oractivated that is borne on the released one of the one or more secondaryMAC entities is automatically transferred to be borne on the master MACentity.
 10. The method according to claim 1, wherein the master MACentity is configured to bear a logical channel corresponding to a bearerfor which packet duplication mode is not configured or activated andlogical channels corresponding to a bearer for which packet duplicationmode is configured or activated; and the one or more secondary MACentities are configured to only bear logical channels corresponding to abearer for which packet duplication mode is configured or activated. 11.The method according to claim 1, further comprising: determining whetherto trigger a buffer state reporting (BSR); and reporting to the networkside buffer sizes of the logical channels or logical channel groupscorresponding to the master MAC entity and the one or more secondary MACentities when it is determined the BSR is to be triggered.
 12. Themethod according to claim 11, wherein the determining whether to triggerthe BSR is performed based on the UE.
 13. The method according to claim12, wherein the reporting to the network side the buffer sizes of thelogical channels or logical channel groups corresponding to the masterMAC entity and the one or more secondary MAC entities comprises:reporting to the network side the buffer sizes of the logical channelsor logical channel groups corresponding to the master MAC entity and theone or more secondary MAC entities by using a carrier corresponding toany one MAC entity of the master MAC entity and the one or moresecondary MAC entities.
 14. The method according to claim 13, whereinthe reporting to the network side the buffer sizes of the logicalchannels or logical channel groups corresponding to the master MACentity and the one or more secondary MAC entities comprises: reportingto the network side the buffer sizes of the logical channels or logicalchannel groups corresponding to the master MAC entity and the one ormore secondary MAC entities through one BSR MAC control element (CE); orreporting to the network side the buffer sizes of the logical channelsor logical channel groups corresponding to the master MAC entity and theone or more secondary MAC entities through a plurality of BSR MAC CEs inone MAC protocol data unit (PDU).
 15. (canceled)
 16. The methodaccording to claim 11, wherein the determining whether to trigger theBSR is performed based on a MAC entity.
 17. The method according toclaim 16, wherein the reporting to the network side the buffer sizes ofthe logical channels or logical channel groups corresponding to themaster MAC entity and the one or more secondary MAC entities comprises:reporting to the network side the buffer sizes of the logical channelsor logical channel groups corresponding to the master MAC entity and theone or more secondary MAC entities by using a carrier corresponding tothe MAC entity or a carrier corresponding to other MAC entity.
 18. Themethod according to claim 14, wherein the reporting to the network sidethe buffer sizes of the logical channels or logical channel groupscorresponding to the master MAC entity and the one or more secondary MACentities comprises: adding identification information in the BSR MAC CEto identify a correspondence between the logical channels or logicalchannel groups and the MAC entities when a carrier used in BSR MAC CEtransmission is not limited and there is a repetition of ID among thelogical channels or logical channel groups corresponding to differentMAC entities.
 19. The method according to claim 1, wherein prior to thetransmitting, by the UE, the duplicated transmission data to thedifferent RLC entities respectively, the method further comprises:transmitting a UE capability to the network side, the UE capabilitycarrying capability indication information indicating that the bearerusing packet duplication mode is supported.
 20. A method of transmittingdata applied to a network side device, comprising: receiving, by amaster medium access control (MAC) entity and one or more secondary MACentities of a network side device, duplicated transmission datatransmitted by a user equipment (UE) through different carriers when apacket duplication mode is configured or activated for a bearer;transmitting, by the master MAC entity and the one or more secondary MACentities, the transmission data to different radio link control (RLC)entities through different logical channels; and transmitting, by theRLC entities, received transmission data to a Packet Data ConvergenceProtocol (PDCP) entity. 21-65. (canceled)
 66. A user equipment (UE),comprising a processor and a memory, wherein the processor is configuredto read and execute a program stored in the memory to implement steps ofthe method according to claim
 1. 67. A network side device, comprising aprocessor and a memory, wherein the processor is configured to read andexecute a program stored in the memory to implement steps of the methodaccording to claim 20.